DNP3 Emerson EIE – Data Groups

Data Groups

With few exceptions, data groups must be defined in a device template file in order for them to be available for use on a remote device. Which data groups are defined by a device template file depends on protocol, device type, and unique configuration.

CygNet distributes sample device template files for its EIEs, each of which typically serves one or more hardware models along with applicable firmware. Therefore, the data groups described in the table below are only those data groups defined by CygNet in sample device template file(s). Your template(s) might not include some of the data groups described below. Device template files exist to enable users to customize device configurations; however, CygNet is not responsible for changes made by users. Three data groups listed below (GasLive, StaStat, and System) are examples of custom data groups and can be modified or deleted. The remaining data groups should not be edited or removed.

For information about data group definitions and device template files, see Device Template Files.

For more information about data group dependencies, see Data Group Dependencies.

Notes:

Point IDs must be unique within a data group (case insensitive).
Data group elements for DNP3 Emerson data groups do not support a conversion function (cvtF).
When point processing is performed on history data groups, only closed records will be published and processed to points. If a device has leading timestamped records and returns the current, open record, point processing will not be performed for that record, even though there is data in the DDS transaction. The point record will be updated only when that record is closed. This is to avoid a situation where a point has multiple entries with the same timestamp, since an open record may be still updating values with each new poll, but each update will have the same timestamp. For example, say you start polling for a daily history record at 8:00am, you’ll get the first value at 8:00am, then if you poll every five minutes, you’ll get new values throughout the day at the exact same timestamp. A history record is basically an array of data with a timestamp and values where the values have different process variables for each incremental poll. The timestamp won’t get written until the record is closed, which happens at the end of the time period, in this case, a day.
Best practice recommends that you do not perform UDC and point processing on FMS data groups. The DEIDs specified in FMS data groups are generic and use the eFMS enumeration to identify the CygNet-defined FMS items referenced in the device template file. No polling is done on these data groups — all data is coming from the native data groups. Points should be mapped to the native data groups since that is the data group that is actually processing the device data. While point processing may work on the FMS data groups, it is not supported, not tested, not consistent across EIEs, and is not recommended practice.

DNP3 Emerson EIE Data Groups

Browse by letter: [A] [C] [D] [E] [F] [G] [H] [I] [M] [S]

Data Group Type

Usage Notes

AllPoints

The "All Points (Class 0)" data group gets all Class 0 static data values. When this data group is polled, CygNet point updates are made to any mapped deids in instantiated data groups with a matching ptId.

Note: The "All Points (Class 0)" data group can be huge — it will get a data value for every single DNP3 item (AI, AO, DI, DO, counter, string, etc…).

For the FB3000 device, this could be thousands of items.

CfgDg

The "Configurable Data Group" data group provides a flexible way to create custom data groups on a per-device basis. See Configurable Data Group for more information.

DateTime

The "Date and Time" data group retrieves the field device's current time and can be used to sync it to the host's current time.

Event

The "Events" data group gets events by class (1, 2, 3) or by point type. The point type option provides a drop-down menu listing variations available for the chosen point type. When this data group is polled, CygNet point updates are made to any mapped deids in instantiated data groups with a matching ptId. See Polling Notes for more information.

The Emerson FB3000 device does not have event-style data enabled by default.

FmsAlarm

The "FMS Alarms" data group is used to send alarm data to FMS. See FMS Alarm Data Group for more information.

Dependencies:

"Hist - Alarms" (HistAlarm)

FmsConfig

The "FMS Configuration" data group is used to bi-directionally transfer meter configuration between a field device and FMS. Data is retrieved from DP, Linear, and Liquid Linear (allocation) meter types. See FMS Configuration Data Group for more information.

Dependencies:

Configuration data groups used for requesting data from the device to send to FMS:
- "Meter Config - DP" (MtrCfgDp)
- "Meter Config - Linear" (MtrCfgLin)
- "Meter Config - Liquid Linear" (MtrCfgLiq)

Configuration data groups for sending gas composition data from FMS to the device:
- Gas Component Config (GasCfg)
- Gas Component Config Apply (GasCfgAply)

FmsEvent

The "FMS Events" data group is used to send event data to the FMS. See FMS Events Data Group for more information.

Dependencies:

"Hist - Events" (HistEvent)

FmsHistD

The "FMS Daily History" data group is used to send historical daily data to FMS. See DNP3 Emerson EIE FMS History Data Groups for more information.

Dependencies:

"Hist - Station Daily" (HistStaD)

FmsHistH

The "FMS Hourly History" data group is used to send historical daily data to FMS. See DNP3 Emerson EIE FMS History Data Groups for more information.

Dependencies:

"Hist - Station Hourly" (HistStaH)

GasCfg

The "Gas Component Config" is used to receive FMS configuration data. This data group is used in conjunction with GasCfgAply to send gas quality information from FMS to the device. See FMS Configuration Data Group for more information.

GasCfgAply

The "Gas Component Config Apply" data group is used to commit any outstanding changes made to gas composition so they will take effect. The GasCfg data group includes the gas composition data. This data group is used in conjunction with GasCfg to send gas quality information from FMS to the device. See FMS Configuration Data Group for more information.

GasLive

"Gas Component Live". This data group is an example of a custom data group that can be modified or deleted. It is not required.

HistAlarm

The "Hist - Alarms" data group is used to read alarms from the Emerson event file. See Hist - Alarms Data Group for more information.

HistCfg

The "Hist - Config" data group reads the configuration for a history data group. See Hist - Config Data Group for more information.

HistEvent

The "Hist - Events" data group is used to read events from the Emerson event file. See Hist - Events Data Group for more information.

HistGenD

The "Hist - General Daily" data group is used to read historical general daily data from a field device. See History Data Groups for more information.

HistGenH

The "Hist - General Hourly" data group is used to read historical general hourly data from a field device. See History Data Groups for more information.

HistGenM

The "Hist - General Monthly" data group is used to read historical general monthly data from a field device. See History Data Groups for more information.

HistGenW

The "Hist - General Weekly" data group is used to read historical general weekly data from a field device. See History Data Groups for more information.

HistStaD

The "Hist - Station Daily" data group is used to read historical station daily data from a field device. See History Data Groups for more information.

HistStaH

The "Hist - Station Hourly" data group is used to read historical station hourly data from a field device. See History Data Groups for more information.

HistStaM

The "Hist - Station Monthly" data group is used to read historical station monthly data from a field device. See History Data Groups for more information.

HistStaW

The "Hist - Station Weekly" data group is used to read historical station weekly data from a field device. See History Data Groups for more information.

HistUser

The "Hist - User" data group is used to read user data from a field device. See History Data Groups for more information.

IntInd

The "Internal Indications" data group displays the IIN values obtained when reading/writing other data groups. The data group is composed of 16 Internal Indication bits that indicate a combination of whether events are available, whether the device needs time, the device status, whether there is an event overflow condition, and the success or failure of a specific request. The IIN bits are part of the header of every packet received from the device and are described in the following table:

IIN Bit Mapping

Bit	Description	Point ID
IIN1.0	All Stations	IIN.0
IIN1.1	Events Class 1	IIN.1
IIN1.2	Events Class 2	IIN.2
IIN1.3	Events Class 3	IIN.3
IIN1.4	Need Time	IIN.4
IIN1.5	Local Control	IIN.5
IIN1.6	Device Trouble	IIN.6
IIN1.7	Device Restart	IIN.7
IIN2.0	Bad Function Code	IIN.8
IIN2.1	Bad Object	IIN.9
IIN2.2	Bad Parameter	IIN.10
IIN2.3	Event Overflow	IIN.11
IIN2.4	Executing	IIN.12
IIN2.5	Config Corrupt	IIN.13
IIN2.6	Reserved 2	IIN.14
IIN2.7	Reserved 1	IIN.15

The "Internal Indications" data group can also be used to clear the "Restart" bit (IIN.7).

See Device Template File Items for more information.

MtrCfgDp

The "Meter Config - DP" data group is used to retrieve FMS configuration data for DP meter types. See FMS Configuration Data Group for more information.

MtrCfgLin

The "Meter Config - Linear" data group is used to retrieve FMS configuration data for Linear meter types. See FMS Configuration Data Group for more information.

MtrCfgLiq

The "Meter Config - Liquid Linear" data group is used to retrieve FMS configuration data for Liquid Linear (allocation) meter types. See FMS Configuration Data Group for more information.

MtrList

The "Meter List" data group is used to retrieve meter information (count, type, content, version, station).

SinglePt

The "Single Point" data group reads from or writes to a point on demand. See Single Point Data Group for more information.

Note: It is recommended that you use this data group to write analog output and binary output values.

StaStat

The "Station Status" data group is used to retrieve station status information (description, volume rate, mass rate, and energy rate). This data group is an example of a custom data group that can be modified or deleted. It is not required.

System

The "System" data group is used to retrieve meter information for DP, Linear, and Liquid Linear (allocation) meter types. This data group is an example of a custom data group that can be modified or deleted. It is not required.